Method, apparatus and computer program product for generating externally shared communication channels

ABSTRACT

Creating a shared communication channel in a group-based communication platform is described. A shared communication channel generation request associated with a first organization identifier and a second organization identifier can be received from a first client associated with the first organization identifier. A shared communication channel acceptance request can be sent to a second client associated with the second organization identifier. Based at least in part on receiving a shared communication channel acceptance notification, wherein the shared communication channel acceptance notification includes an electronic approval to associate the shared communication channel identifier with the first organization identifier and the second organization identifier, transmitting, to each of the first client and the second client, a shared group-based communication channel interface of the shared communication channel.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to and is a continuation of U.S. patentapplication Ser. No. 16/576,085, filed on Sep. 19, 2019, which is acontinuation of U.S. patent application Ser. No. 15/655,634, filed Jul.20, 2017, which issued as U.S. Pat. No. 10,541,825 on Jan. 21, 2020, theentire contents of each of which are incorporated herein by reference.

BACKGROUND

Various systems are configured to create externally shared communicationchannels. Applicant has identified many deficiencies and problemsassociated with existing systems. Through applied effort, ingenuity, andinnovation, many of these identified deficiencies and problems have beensolved by developing solutions that are in accordance with theembodiments of the present invention, many examples of which aredescribed in detail herein.

BRIEF SUMMARY

In general, embodiments of the present invention provide methods,apparatus, systems, computing devices, and/or the like for generatingexternally shared communication channels.

In accordance with one aspect, a computer-implemented method product forcreating an externally shared communication channel in a group-basedcommunication platform is provided. The group-based communicationplatform may have a plurality of database shards. Thecomputer-implemented method may include receiving, from a first clientdevice associated with an initiator group identification, a sharedcommunication channel generation query associated with the initiatorgroup identification and a target group identification; generating, inthe group-based communication platform, a shared communication channelshard, wherein the shared communication channel shard is assigned ashared communication channel identification, and the group-basedcommunication platform includes a first database shard associated withthe initiator group identification and a second database shardassociated with the target group identification; transmitting, to asecond client device associated with the target group identification, ashared communication channel acceptance request, wherein the sharedcommunication channel acceptance request is associated with the sharedcommunication channel identification; receiving a shared communicationchannel acceptance notification, wherein the shared communicationchannel acceptance notification includes an electronic approval toassociate the shared communication channel identification with thetarget group identification; updating, in a main database, a shardreferential table based on the initiator group identification, thetarget group identification, and the shared communication channelidentification; and transmitting, to each of the first client device andthe second client device, an externally shared group-based sharedcommunication channel interface of the shared communication channelbased on the shared communication channel shard.

In accordance with another aspect, the shard referential table includesa first referential connection between the initiator groupidentification and the first database shard, and a second referentialconnection between the target group identification and the seconddatabase shard.

In accordance with another aspect, updating the shard referential tablemay further include identifying, based on the initiator groupidentification, the first referential connection in the shardreferential table; identifying, based on the target groupidentification, the second referential connection in the shardreferential table; and generating a third referential connection betweenthe first referential connection, the second referential connection, andthe shared communication channel identification.

In accordance with another aspect, a computer-implemented method ofupdating a group-based communication interface of a client device isprovided. The group-based communication interface may define a channellist pane comprising a plurality of group-based communication channelsand a channel messaging pane. The method may include receiving anexternally shared communication channel generation request, wherein theexternally shared communication channel generation request includes afirst group identification and a second group identification;determining whether the client device is associated with one of thefirst group identification or the second group identification; and inresponse to determining that the client device is associated with one ofthe first group identification or the second group identification,generating, in the channel list pane, an externally shared communicationchannel list subpane.

In accordance with another aspect, the externally shared communicationchannel list subpane indicates a list of one or more externally sharedcommunication channels associated with the client device

In accordance with another aspect, the externally shared communicationchannel generation request further includes a first externally sharedcommunication channel indicator associated with the first groupidentification, and a second externally shared communication channelindicator associated with the second group identification, whereingenerating, in the channel list pane, the externally sharedcommunication channel list subpane further includes: in response todetermining that the client device is associated with the first groupidentification, displaying, in the externally shared communicationchannel list subpane, the first externally shared communication channelindicator; and in response to determining that the client device isassociated with the second group identification, displaying, in theexternally shared communication channel list subpane, the secondexternally shared communication channel indicator.

In accordance with another aspect, an apparatus comprising at least oneprocessor and at least one non-transitory memory is provided. In someembodiments, the at least one non-transitory memory and the program codeconfigured to, with the processor, cause the apparatus to at leastreceive, from a first client device associated with an initiator groupidentification, a shared communication channel generation queryassociated with the initiator group identification and a target groupidentification; generate, in the group-based communication platform, ashared communication channel shard, wherein the shared communicationchannel shard is assigned a shared communication channel identification,and the group-based communication platform includes a first databaseshard associated with the initiator group identification and a seconddatabase shard associated with the target group identification;transmit, to a second client device associated with the target groupidentification, a shared communication channel acceptance request,wherein the shared communication channel acceptance request isassociated with the shared communication channel identification; receivea shared communication channel acceptance notification, wherein theshared communication channel acceptance notification includes anelectronic approval to associate the shared communication channelidentification with the target group identification; update, in a maindatabase, a shard referential table based on the initiator groupidentification, the target group identification, and the sharedcommunication channel identification; and transmit, to each of the firstclient device and the second client device, an externally sharedgroup-based shared communication channel interface of the sharedcommunication channel based on the shared communication channel shard.

In accordance with another aspect, a computer program product isprovided. The computer program product may comprise at least onecomputer-readable storage medium having computer-readable program codeportions stored therein, the computer-readable program code portionscomprising executable portions configured to receive, from a firstclient device associated with an initiator group identification, ashared communication channel generation query associated with theinitiator group identification and a target group identification;generate, in the group-based communication platform, a sharedcommunication channel shard, wherein the shared communication channelshard is assigned a shared communication channel identification, and thegroup-based communication platform includes a first database shardassociated with the initiator group identification and a second databaseshard associated with the target group identification; transmit, to asecond client device associated with the target group identification, ashared communication channel acceptance request, wherein the sharedcommunication channel acceptance request is associated with the sharedcommunication channel identification; receive a shared communicationchannel acceptance notification, wherein the shared communicationchannel acceptance notification includes an electronic approval toassociate the shared communication channel identification with thetarget group identification; update, in a main database, a shardreferential table based on the initiator group identification, thetarget group identification, and the shared communication channelidentification; and transmit, to each of the first client device and thesecond client device, an externally shared group-based sharedcommunication channel interface of the shared communication channelbased on the shared communication channel shard.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described some embodiments in general terms, references willnow be made to the accompanying drawings, which are not necessarilydrawn to scale, and wherein:

FIG. 1 is an exemplary system architecture diagram of a group-basedcommunication platform in accordance with some embodiments of thepresent invention;

FIG. 2 is an exemplary schematic diagram of a message server inaccordance with some embodiments of the present invention;

FIG. 3 is an exemplary schematic diagram of a network application serverin accordance with some embodiments of the present invention;

FIG. 4 is an exemplary flow chart illustrating an exemplary method inaccordance with some embodiments of the present invention;

FIG. 5 is an exemplary flow chart illustrating an exemplary method inaccordance with some embodiments of the present invention;

FIG. 6 is an exemplary flow chart illustrating an exemplary method inaccordance with some embodiments of the present invention;

FIG. 7 is an exemplary flow chart illustrating an exemplary method inaccordance with some embodiments of the present invention; and

FIGS. 8A, 8B, 8C, and 8D illustrate various elements of exemplary userinterfaces in accordance with some embodiments of the present invention.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Various embodiments of the present invention now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. The terms“illustrative” and “exemplary” are used to be examples with noindication of quality level. Like numbers refer to like elementsthroughout.

Overview

Various embodiments of the invention relate generally to the creation ofexternally shared communication channels in a group-based communicationplatform. The group-based communication platform is configured tocommunicate with a plurality of client devices and operates a pluralityof network databases. Each of the client devices may be associated witha group identification, which may indicate a group or an organizationthat the client device is associated with. For example, a particularorganization may have a plurality of client devices connected to agroup-based communication platform, and the group-based communicationplatform identifies each client device as being associated with thatparticular organization.

The group-based communication platform also includes a plurality ofdatabase shards, and each database shard stores data related to aparticular group identification. For example, a database shard may storeelectronic communication data associated with members of a particularorganization, which enables members of that particular organization tocommunicate and exchange data with other members of the sameorganization in real-time. In this example, the organization itself isthe owner of the database shard, and has control over where and how therelated data is stored. This simplifies many technical tasks, such asdata retention, unfurling, and integration settings.

However, existing systems and approaches are plagued by many technicalrestrictions and limitations, as they do not provide support for dataexchange and communication between different organizations, as eachdatabase shard can only be owned by a single organization. For example,when a user Tony of organization X intends to share data (stored in theorganization X's database shard) with another user Frank of organizationY, Tony will have to exchange said data through other communicationmeans, which may cause communication delays and inefficiencies. As datacan be time-sensitive and dynamic in nature, technical limitations ofexisting systems may compromise data integrity and deplete networkresources.

In addition, existing systems are not configured to manage useridentities in externally shared communication channels. For example,Tony may be a member of both organization X and organization Z. Tony mayhave an identity (“Tony-X”) associated with communication channels inorganization X, and another identity (“Tony-Z”) associated withcommunication channels in organization Z. In an externally sharedcommunication channel connecting organization X and organization Z,existing systems are unable to reconcile “Tony-X” and “Tony-Z,” and mayfalsely determine that “Tony-X” and “Tony-Z” are two differentindividuals. Existing systems may determine Tony as a member atorganization X, but as an individual or a guest at organization Z, whichmay create conflicts in data management.

Systems structured in accordance with various embodiments of theinvention overcome challenges faced by existing systems.

Continuing from the “Tony to Frank” discussion above, Tony in agroup-based communication platform (e.g. a cloud-based groupcollaboration tool provided by SLACK®) that is structured in accordancewith various embodiments of the invention is able to exchange data inreal-time with Frank through an externally shared communication channel.In other words, members of organization X and organization Y are able toview content and share data in the externally shared communicationchannel as if they belong to the same organization. Network applicationsand other software integrations continue to work in the externallyshared communication channel, and each organization maintains its ownpreferences that apply to its respective channel experience.

Continuing from the “Tony-X/Tony-Z” discussion above, in a group-basedcommunication platform that is structured in accordance with variousembodiments of the invention, Tony is assigned an unified identity thatrecognizes Tony as a member of both organization X and organization Z.In other words, the cloud-based group collaboration tool provided bySLACK® is able to create union of identities that may recognizeindividuals as members of separate teams.

From the user experience perspective, systems structured in accordancewith various embodiments of the invention greatly enhance organizationalproductivity and efficiency. They also reduce the need for other formsof communications (such as electronic mail), and provide bettercollaboration between different organizations while eliminating channeldisconnections between teams. In addition, they are configured toprovide asymmetrical and customizable privacy settings, where anexternally shared communication channel between two teams may have oneprivacy configuration for one team and a different configuration for theother. Further, externally shared communication channels may createcross-network effects, which increases user retention rates fromdifferent organizations or different groups.

From the developer's perspective, systems structured in accordance withvarious embodiments of the invention provide support for the retrievaland appropriate visibility of data, while providing the flexibility ofretention settings. They also enable the selective connection ofchannels, as well as teams based on channels.

As such, systems structured in accordance with various embodiments ofthe invention provide specific, technical solutions to technicalproblems faced by existing systems, the details of which are describedhereinafter.

Definitions

As used herein, the terms “data,” “content,” “information,” and similarterms may be used interchangeably to refer to data capable of beingtransmitted, received, and/or stored in accordance with embodiments ofthe present invention. Thus, use of any such terms should not be takento limit the spirit and scope of embodiments of the present invention.Further, where a computing device is described herein to receive datafrom another computing device, it will be appreciated that the data maybe received directly from another computing device or may be receivedindirectly via one or more intermediary computing devices, such as, forexample, one or more servers, relays, routers, network access points,base stations, hosts, and/or the like. Similarly, where a computingdevice is described herein to send data to another computing device, itwill be appreciated that the data may be sent directly to anothercomputing device or may be sent indirectly via one or more intermediarycomputing devices, such as, for example, one or more servers, relays,routers, network access points, base stations, hosts, and/or the like.

The term “user” should be understood to refer to an individual, a groupof individuals, business, organization, and the like. Users may access agroup-based communication or messaging system using client devices.“Group-based” is used herein to refer to a system, channel, message, orvirtual environment that has security sufficient such that it isaccessible only to a defined group of users. The group may be defined bycommon access credentials such as those of an organization or commercialenterprise. Access may further be facilitated by a validated request tojoin or an invitation to join transmitted by one group member user toanother non-member user. Group identifiers (defined below) are used toassociate data, information, messages, etc., with specific groups.

The terms “user profile,” “user account,” and “user account details”refer to information associated with a user, including, for example, auser identifier, one or more group-based communication channelidentifiers associated with group-based communication channels that theuser has been granted access to, one or more group identifiers forgroups with which the user is associated, an indication as to whetherthe user is an owner of any group-based communication channels, anindication as to whether the user has any group-based communicationchannel restrictions, a plurality of messages, a plurality of emojis, aplurality of conversations, a plurality of conversation topics, anavatar, an email address, a real name (e.g., John Doe), a username(e.g., jdoe), a password, a real name, a time zone, a status, and thelike. The user account details can include a subset designation of usercredentials, such as, for example, login information for the userincluding the user's username and password.

The term “client device” refers to computer hardware(s) and/orsoftware(s) that is/are configured to access one or more services madeavailable by one or more servers. The server(s) is/are often (but notalways) on another computer system, in which case the client deviceaccesses the service by way of a network. A client device may beassociated with a group identification, where the group identificationis an electronic indication that suggests a group (e.g. user group) thatthe user belongs to. Client devices may include, without limitation,smart phones, tablet computers, laptop computers, desktop computers,wearable devices, personal computers, enterprise computers, and thelike.

The term “group-based communication platform” refers to a collection ofcomputing services that are accessible to one or more client devices,and that are operable to provide access to a plurality of softwareapplications related to operations of databases. In some examples, thegroup-based communication platform may take the form of one or morecentral servers disposed in communication with one or more additionalservers running software applications, and having access to one or moredatabases storing digital content items, application-related data,and/or the like. The group-based communication platform may also supportclient retention settings and other compliance aspects. Further, thegroup-based communication platform may provide comprehensive third partydeveloper support that grants appropriate access to the data and allowsthird parties to build applications and bots to integrate withcustomer's workflows.

The term “communication channel” refers to an information route andassociated circuitry that is used for data exchange between and amongsystems and parts of systems. For example, a communication channel maybe established between and among various client devices, allowing theseclient devices to communicate and share data between and among eachother. A communication channel identification may be assigned to acommunication channel, which indicates the physical address in adatabase where related data of that communication channel is stored. Acommunication channel may be “public,” which may allow any client deviceto join and participate in the information sharing through thecommunication channel. A communication channel may be “private,” whichmay restrict data communications in the communication channel to certainclient devices and/or users.

The term “group-based communication channel interface” refers to avirtual communications environment or feed that is configured to displaymessaging communications posted by channel members (e.g., validatedusers accessing the environment using client devices) that are viewableonly to the members of the group. The format of the group-basedcommunication channel may appear differently to different members of thegroup-based communication channel; however, the content of thegroup-based communication channel (i.e., messaging communications) willbe displayed to each member of the group-based communication channel.For instance, a common set of group-based messaging communications willbe displayed to each member of the respective group-based communicationchannel such that the content of the group-based communication channel(i.e., messaging communications) will not vary per member of thegroup-based communication channel.

As used herein, the terms “messaging communication” and “message” referto any electronically generated digital content object provided by auser using a client device and that is configured for display within agroup-based communication channel. Message communications may includeany text, image, video, audio, or combination thereof provided by a user(using a client device). For instance, the user may provide a messagingcommunication that includes text as well as an image and a video withinthe messaging communication as message contents. In such a case, thetext, image, and video would comprise the messaging communication ordigital content object. Each message sent or posted to a group-basedcommunication channel of the group-based communication system includesmetadata comprising the following: a sending user identifier, a messageidentifier, message contents, a group identifier, and a group-basedcommunication channel identifier. Each of the foregoing identifiers maycomprise ASCII text, a pointer, a memory address, and the like.

The terms “group-based communication channel identifier” or “channelidentifier” refer to one or more items of data by which a group-basedcommunication channel may be identified. For example, a group-basedcommunication channel identifier may comprise ASCII text, a pointer, amemory address, and the like.

The terms “group identifier” or “team identifier” refer to one or moreitems of data by which a group within a group-based communication systemmay be identified. For example, a group identifier may comprise ASCIItext, a pointer, a memory address, and the like.

A “sending user identifier” is associated with a collection of messagesthat are sent by a particular user (i.e., a client device associatedwith the particular user). These messages may be analyzed to determinecontext regarding the user (e.g., the user's expertise or interest in atopic may be determined based on the frequency of mention of the topicor key words associated with the topic within such messages).

Group-based communication system users are organized into organizationgroups (e.g., employees of each company may be a separate organizationgroup) and each organization group may have one or more group-basedcommunication channels (explained below) to which users may be assignedor which the users may join (e.g., group-based communication channelsmay represent departments, geographic locations such as offices, productlines, user interests, topics, issues, and/or the like). A groupidentifier may be used to facilitate access control for a message (e.g.,access to the message, such as having the message return as part ofsearch results in response to a search query, may be restricted to thoseusers having the group identifier associated with their user profile).The group identifier may be used to determine context for the message(e.g., a description of the group, such as the name of an organizationand/or a brief description of the organization, may be associated withthe group identifier).

Group-based communication system users may join group-basedcommunication channels. Some group-based communication channels may beglobally accessible to those users having a particular organizationalgroup identifier associated with their user profile (i.e., users who aremembers of the organization). Access to some group-based communicationchannels may be restricted to members of specified groups, whereby thegroup-based communication channels are accessible to those users havinga particular group identifier associated with their user profile. Thegroup-based communication channel identifier may be used to facilitateaccess control for a message (e.g., access to the message, such ashaving the message return as part of search results in response to asearch query, may be restricted to those users having the group-basedcommunication channel identifier associated with their user profile, orwho have the ability to join the group-based communication channel). Thegroup-based communication channel identifier may be used to determinecontext for the message (e.g., a description of the group-basedcommunication channel, such as a description of a project discussed inthe group-based communication channel, may be associated with thegroup-based communication channel identifier).

The term “private group-based communication channel” refers to agroup-based communication channel with restricted access such that it isnot generally accessible and/or searchable by other members of thegroup-based communication system. For example, only those users oradministrators who have knowledge of and permission to access (e.g., agroup-based communication channel identifier for the private group-basedcommunication channel is associated with their user profile after theuser has been validated/authenticated) the private group-basedcommunication channel may view content of the private group-basedcommunication channel.

The term “query” refers to a request associated with a database. A“query” may be generated on one or more client devices, and may betransmitted to a group-based communication platform. A query may be a“select query,” which is used to extract data from the database in areadable format according to the query. A query may be an “actionquery,” which asks for operations (such as insertion, deletion, and/orupdating) on the data stored in a network database. For example, a“communication channel generation query” is an action query thatrequests the generation of a communication channel.

The term “shard” refers to a collection of related, discrete items ofdata that may be accessed and managed individually. A shard may bestored in a single database, or optionally spread across multipledatabases. This is particularly beneficial when there is a large amountof data. The cost of creating and maintaining a very large database inone place can increase exponentially because the database will requiremore high-end computers. In contrast, database shards can be distributedacross a number of much less expensive commodity databases. “Sharding”refers to partitioning a large database to make it more manageable.Because sharding a database involves breaking up the database intosmaller databases that share nothing in common, it causes technicaldifficulties to create a communication channel that involves two or moredatabase shards. Database may be “sharded” based on a variety offactors, including, but not limited to, channel identifications, useridentifications, team identifications, or any attribute of data withindatabase structure. To determine which factor(s) to use, the system mayconsider data isolation, proximity of data (for the purposes of lookup),and performance/speed of access across a distributed system. The systemmay need to take into account both the volume of data and the speed withwhich the system is required to retrieve such data.

The term “referential table” refers to a set of referential connectionsbetween and among various data items. A referential table may be in atabular form, which may include “rows” and “columns.” Each row mayrepresent a referential connection, and each column may represent a dataitem. A data item may be a group identification, a channelidentification, a physical address in a network database, and the like.A referential connection may indicate the relationships and/orconstraints between and among various data items. For example, a shardreferential table may identify a physical address of a communicationchannel shard in a network database based on an identification of thatcommunication channel. The shard referential table may includeparameters, such as database shard parameter, message server shardparameter, redis shard parameter, solr shard parameter, team metadata(e.g., date create, date archive, date delete), admin user data, domain,email domain, preferences, invites, credits, payment tier, and dataindicating whether the team is an enterprise.

The term “event” refers to identifiable, non-transitory occurrence thathas technical significance for system hardware and/or software. An eventmay represent some message, token, count, pattern, value, or marker thatcan be recognized by a computer system. An application may be triggeredto perform certain functions based on the event. For example, in agroup-based communication channel, a message sent by a user is an eventfor applications that utilize the event application programminginterface (API). An event may be user-generated, such as keystrokes ormouse movements, or system-generated, such as program loading anderrors.

Example System Architecture

Methods, apparatuses, and computer program products of the presentinvention may be embodied by any of a variety of devices. For example,the method, apparatus, and computer program product of an exampleembodiment may be embodied by a network device, such as a server orother network entity, configured to communicate with one or moredevices, such as one or more client devices. In some preferred andnon-limiting embodiments, the computing device may include fixedcomputing devices, such as a personal computer or a computerworkstation. Still further, example embodiments may be embodied by anyof a variety of mobile devices, such as a portable digital assistant(PDA), mobile phone, smartphone, laptop computer, tablet computer,wearable device, or any combination of the aforementioned devices.

FIG. 1 illustrates an example computing system 100 within whichembodiments of the present invention may operate. Users may access agroup-based communication platform 105 via a communication network 103using client devices 101A-101N.

Communication network 103 may include any wired or wirelesscommunication network including, for example, a wired or wireless localarea network (LAN), personal area network (PAN), metropolitan areanetwork (MAN), wide area network (WAN), or the like, as well as anyhardware, software and/or firmware required to implement it (such as,e.g., network routers, etc.). For example, communication network 103 mayinclude a cellular telephone, an 802.11, 802.16, 802.20, and/or WiMaxnetwork. Further, the communication network 103 may include a publicnetwork, such as the Internet, a private network, such as an intranet,or combinations thereof, and may utilize a variety of networkingprotocols now available or later developed including, but not limited toTCP/IP based networking protocols. For instance, the networking protocolmay be customized to suit the needs of the group-based communicationsystem. In some embodiments, the protocol is a custom protocol of JSONobjects sent via a Websocket channel. In some embodiments, the protocolis JSON over RPC, JSON over REST/HTTP, and the like.

The group-based communication platform 105 may include a message server107 and a network application server 109. The network application server109 may communicate with a main database 111 and one or more databaseshards 113A-113N.

The message server 107 may be embodied as a computer or computers asknown in the art. The message server 107 may provide for receivingelectronic data from various sources, including, but not limited to, theclient devices 101A-101N via the communication network 103. For example,the message server 107 may be operable to receive and process electronicmessages provided by the client devices 101A-101N. The message server107 may also facilitate transmission and amplification of electronicmessages to the client devices 101A-101N.

Similarly, the network application server 109 may be embodied as acomputer or computers as known in the art. The network applicationserver 109 may provide for receiving electronic data from varioussources, including, but not limited to, the client devices 101A-101N viathe communication network 103. For example, the network applicationserver 109 may be operable to receive and process electronic messagesprovided by the client devices 101A-101N. The network application server109 may also be operable to receive and process network database queriesprovided by the client devices 101A-101N and/or the message server 107regarding the main database 111 and/or one or more database shards113A-113N. The network application server 109 may further facilitate thegeneration of user interfaces.

The client devices 101A-101N may be any computing device as definedabove. Electronic data received by the message server 107 and thenetwork application server 109 from the client devices 101A-101N may beprovided in various forms and via various methods.

In some preferred and non-limiting embodiments, one or more of theclient devices 101A-101N are mobile devices, such as smartphones ortablets. The one or more client devices may execute an “app” to interactwith the message server 107 and/or network application server 109. Suchapps are typically designed to execute on mobile devices, such assmartphones or tablets. For example, an app may be provided thatexecutes on mobile device operating systems such as Apple Inc.'s iOS©,Google Inc.'s Android©, or Microsoft Inc.'s Windows 10 Mobile*. Theseplatforms typically provide frameworks that allow apps to communicatewith one another, and with particular hardware and software componentsof mobile devices. For example, the mobile operating systems named aboveeach provides frameworks for interacting with location servicescircuitry, wired and wireless network interfaces, user contacts, andother applications. Communication with hardware and software modulesexecuting outside of the app is typically provided via applicationprogramming interfaces (APIs) provided by the mobile device operatingsystem.

In some preferred and non-limiting embodiments, the client devices101A-101N may interact with the message server 107 and/or networkapplication server 109 via a web browser. The client devices 101A-101Nmay also include various hardware or firmware designed to interact withthe message server 107 and/or network application server 109.

In some preferred and non-limiting embodiments, the database shards113A-113N may be embodied as a data storage device such as a networkattached storage (NAS) device or devices, or as a separate databaseserver or servers. The database shards 113A-113N include informationaccessed and stored by the network application server 109. For example,the database shards 113A-113N may include, without limitation, userprofiles, user privilege information, electronic files, messagingcommunications organized among a plurality of group-based communicationchannels, and/or the like.

In some preferred and non-limiting embodiments, the main database 111may be embodied as a data storage device such as a network attachedstorage (NAS) device or devices, or as a separate database server orservers. The main database 111 includes information accessed and storedby the network application server 109. For example, the main database111 may include, without limitation, a shard referential table.

In some embodiments of an exemplary group-based communication platform105, a message or messaging communication may be sent from a clientdevice 101A-101N to a group-based communication platform 105. In variousimplementations, messages may be sent to the group-based communicationplatform 105 over communication network 103 directly by one of theclient devices 101A-101N. The messages may be sent to the group-basedcommunication platform 105 via an intermediary such as a message server,and/or the like. For example, a client device 101A-101N may be adesktop, a laptop, a tablet, a smartphone, and/or the like that isexecuting a client application (e.g., a group-based communication app).In one implementation, the message may include data such as a messageidentifier, sending user identifier, a group identifier, a group-basedcommunication channel identifier, message contents (e.g., text, emojis,images, links), attachments (e.g., files), message hierarchy data (e.g.,the message may be a reply to another message), third party metadata,and/or the like. In one embodiment, the client device 101A-101N mayprovide the following example message, substantially in the form of a(Secure) Hypertext Transfer Protocol (“HTTP(S)”) POST message includingeXtensible Markup Language (“XML”) formatted data, as provided below:

POST /authrequest.php HTTP/1.1 Host: www.server.com Content-Type:Application/XML Content-Length: 667 <?XML version = “1.0” encoding =“UTF-8”?> <auth_request>  <timestamp>2020-12-31 23:59:59</timestamp> <user_accounts_details>   <user_account_credentials>   <user_name>ID_user_1</user_name>    <password>abc123</password>   //OPTIONAL <cookie>cookieID</cookie>    //OPTIONAL<digital_cert_link>www.mydigitalcertificate.com/JohnDoeDaDoeDoe@gmail.com/mycertifcate.dc</digital_cert_link>   //OPTIONAL <digital_certificate>_DATA_</digital_certificate>  </user_account_credentials>  </user_accounts_details> <client_details>//iOS Client with App and Webkit    //it should benoted that although several client details    //sections are provided toshow example variants of client    //sources, further messages willinclude only on to save    //space   <client_IP>10.0.0.123</client_IP>  <user_agent_string>Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1 like MacOS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D201Safari/9537.53</user_agent_string>  <client_product_type>iPhone6,1</client_product_type>  <client_serial_number>DNXXX1X1XXXX</client_serial_number>  <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_UDID>  <client_OS>iOS</client_OS>  <client_OS_version>7.1.1</client_OS_version>   <client_app_type>appwith webkit</client_app_type>  <app_installed_flag>true</app_installed_flag>  <app_name>MSM.app</app_name>   <app_version>1.0</app_version>  <app_webkit_name>Mobile Safari</client_webkit_name>  <client_version>537.51.2</client_version>  </client_details> <client_details>//iOS Client with Webbrowser  <client_IP>10.0.0.123</client_IP>   <user_agent_string>Mozilla/5.0(iPhone; CPU iPhone OS 7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML,like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53</user_agent_string>  <client_product_type>iPhone6,1</client_product_type>  <client_serial_number>DNXXX1X1XXXX</client_serial_number>  <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_UDID>  <client_OS>iOS</client_OS>  <client_OS_version>7.1.1</client_OS_version>   <client_app_type>webbrowser</client_app_type>   <client_name>Mobile Safari</client_name>  <client_version>9537.53</client_version>  </client_details> <client_details>//Android Client with Webbrowser  <client_IP>10.0.0.123</client_IP>   <user_agent_string>Mozilla/5.0(Linux; U; Android 4.0.4; en-us; Nexus S Build/IMM76D)AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 MobileSafari/534.30</user_agent_string>   <client_product_type>NexusS</client_product_type>   <client_serial_number>YXXXXXXXXZ</clientserial number>   <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXX</client_UDID>   <client_OS>Android</client_OS>  <client_OS_version>4.0.4</client_OS_version>   <client_app_type>webbrowser</client_app_type>   <client_name>Mobile Safari</client_name>  <client_version>534.30</client_version>  </client_details> <client_details>//Mac Desktop with Webbrowser  <client_IP>10.0.0.123</client_IP>   <user_agent_string>Mozilla/5.0(Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.75.14 (KHTML, likeGecko) Version/7.0.3 Safari/ 537.75.14</user_agent_string>  <client_product_type>MacPro5,1</client_product_type>  <client_serial_number>YXXXXXXXXZ</client serial number>  <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX- XXXXXXXXXXXXX</client_UDID>  <client_OS>Mac OS X</client_OS>  <client_OS_version>10.9.3</client_OS_version>   <client_app_type>webbrowser</client_app_type>   <client_name>Mobile Safari</client_name>  <client_version>537.75.14</client_version>  </client_details> <message>   <message_identifier>ID_message_10</message_identifier>  <team_identifier>ID_team_1</team_identifier>  <channel_identifier>ID_channel_1</channel_identifier>   <contents>Thatis an interesting invention. I have attached a copy our patent policy.</contents>   <attachments>patent_policy.pdf</attachments> </message> </auth_request>

The group-based communication platform 105 comprises at least onemessage server 107 that may create a storage message based upon thereceived message to facilitate message indexing and storage in one ormore database shards 113A-113N. In one implementation, the storagemessage may include data such as a message identifier, a groupidentifier, a group-based communication channel identifier, a sendinguser identifier, topics, responses, message contents, attachments,message hierarchy data, third party metadata, conversation primitivedata, and/or the like. For example, the group-based communication server106 may provide the following example storage message, substantially inthe form of a HTTP(S) POST message including XML-formatted data, asprovided below:

POST /storage_message.php HTTP/1.1 Host: www.server.com Content-Type:Application/XML Content-Length: 667 <?XML version = “1.0” encoding =“UTF-8”?> <storage_message> <message_identifier>ID_message_10</message_identifier> <team_identifier>ID_team_1</team_identifier> <channel_identifier>ID_channel_1</channeljdentifier> <sending_user_identifier>ID_user_1</sending_user_identifier>  <topics>  <topic>inventions</topic>   <topic>patents</topic>  <topic>policies</topic>  </topics>  <responses>   <response>liked byID_user_2</response>   <response>starred by ID_user_3</response> </responses>  <contents>That is an interesting invention. I haveattached a copy  our patent policy.</contents> <attachments>patent_policy.pdf</attachments>  <conversation_primitive>  conversation includes messages: ID_message_8, ID_message_9,  ID_message_10, ID_message_11, ID_message_12  </conversation_primitive></storage_message>

In some embodiments, a group identifier as defined above may beassociated with the message. In some embodiments, a group-basedcommunication channel identifier as defined above may be associated withthe message.

In some embodiments, a sending user identifier as defined above may beassociated with the message. In one implementation, the message may beparsed (e.g., using PUP commands) to determine a sending user identifierof the user who sent the message.

In some embodiments, data indicating responses may be associated withthe message. For example, responses to the message by other users mayinclude reactions (e.g., selection of an emoji associated with themessage, selection of a “like” button associated with the message),clicking on a hyperlink embedded in the message, replying to the message(e.g., posting a message to the group-based communication channel inresponse to the message), downloading a file associated with themessage, sharing the message from one group-based communication channelto another group-based communication channel, pinning the message,starring the message, and/or the like. In one implementation, dataregarding responses to the message by other users may be included withthe message, and the message may be parsed (e.g., using PUP commands) todetermine the responses. In another implementation, data regardingresponses to the message may be retrieved from a database. For example,data regarding responses to the message may be retrieved via a MySQLdatabase command similar to the following:

-   -   SELECT messageResponses    -   FROM MSM_Message    -   WHERE messageID=ID_message_10.

For example, data regarding responses to the message may be used todetermine context for the message (e.g., a social score for the messagefrom the perspective of some user). In another example, data regardingresponses to the message may be analyzed to determine context regardingthe user (e.g., the user's expertise in a topic may be determined basedon the responses to the user's message regarding the topic).

In embodiments, attachments may be included with the message. If thereare attachments, files may be associated with the message. In oneimplementation, the message may be parsed (e.g., using PHP commands) todetermine file names of the attachments. For example, file contents maybe analyzed to determine context for the message (e.g., a patent policydocument may indicate that the message is associated with the topic“patents”).

In embodiments, third party metadata may be associated with the message.For example, third party metadata may provide additional contextregarding the message or the user that is specific to a company, group,group-based communication channel, and/or the like. In oneimplementation, the message may be parsed (e.g., using PHP commands) todetermine third party metadata. For example, third party metadata mayindicate whether the user who sent the message is an authorizedrepresentative of the group-based communication channel (e.g., anauthorized representative may be authorized by the company to respond toquestions in the group-based communication channel).

In embodiments, a conversation primitive may be associated with themessage. In one implementation, a conversation primitive is an elementused to analyze, index, store, and/or the like messages. For example,the message may be analyzed by itself, and may form its own conversationprimitive. In another example, the message may be analyzed along withother messages that make up a conversation, and the messages that makeup the conversation may form a conversation primitive. In oneimplementation, the conversation primitive may be determined as themessage, a specified number (e.g., two) of preceding messages and aspecified number (e.g., two) of following messages. In anotherimplementation, the conversation primitive may be determined based onanalysis of topics discussed in the message and other messages (e.g., inthe channel) and/or proximity (e.g., message send order proximity,message send time proximity) of these messages.

In embodiments, various metadata, determined as described above, and/orthe contents of the message may be used to index the message (e.g.,using the conversation primitive) to facilitate various facets ofsearching (i.e., search queries that return results from the messageserver 107). In one implementation, a storage message may be sent fromgroup-based communication server 106 to facilitate indexing in themessage server 107. In another implementation, metadata associated withthe message may be determined and the message may be indexed in themessage server 107. In one embodiment, the message may be indexed suchthat a company's or a group's messages are indexed separately (e.g., ina separate index associated with the group and/or company that is notshared with other groups and/or companies). In one implementation,messages may be indexed at a separate distributed repository (e.g., tofacilitate data isolation for security purposes).

If there are attachments associated with the message, file contents ofthe associated files may be used to index such files in the messageserver 107 to facilitate searching. In one embodiment, the files may beindexed such that a company's or a group's files are indexed at aseparate distributed repository.

An example of electronic information exchange among one or more clientdevices 101A-101N and the group-based communication platform 105 isdescribed below.

The one or more client devices 101A-101N are configured to generate oneor more shared communication channel generation queries associated withthe database shards 113A-113N. Continuing from the “Tony to Frank”discussion, Tony may use client device 101A (having a groupidentification associated with organization X) to generate a sharedcommunication channel generation query, requesting the creation of anexternally shared communication channel with Frank's client device 101(having a group identification associated with organization Y).Organization X and organization Y are each associated with a separateshard of database shards 113A-113N. The shared communication channelgeneration query may be transmitted to the group-based communicationplatform 105 via the communication network 103.

Upon receiving the one or more shared communication channel generationqueries from the one or more client devices 101A-101N, the group-basedcommunication platform 105 may utilize the network application server109 to generate one or more database shards based on the one or moreshared communication channel generation queries. The network applicationserver 109 may further assign a shared communication channelidentification to each of the one or more generated database shards.Continuing from the previous example, the network application server 109may generate a database shard 113N based on the shared communicationchannel generation query provided by Tony via the client device 101A,and may associate a shared communication channel identification with thedatabase shard 113N.

After generating one or more database shards based on one or more sharedcommunication channel generation queries, the group-based communicationplatform 105 may transmit one or more shared communication channelacceptance requests to one or more client devices 101A-101N. Continuingfrom the previous example, the group-based communication platform 105may transmit a shared communication channel acceptance request to clientdevice 101B (Frank), which is indicated in the shared communicationchannel generation query provided by client device 101A (Tony).

Upon receiving the shared communication channel acceptance request, theone or more client devices 101A-101N may generate one or more electronicapprovals, and may transmit these electronic approvals to thegroup-based communication platform 105. Continuing from the previousexample, Frank, via client device 101B, may generate an electronicapproval in response to the shared communication channel acceptancerequest. The electronic approval may indicate Frank's acceptance of theshared communication channel generation query provided by Tony. Theclient device 101B may further transmit the electronic approval to thegroup-based communication platform 105.

Upon receiving the one or more electronic approvals from one or moreclient devices 101A-101N, the group-based communication platform 105associates the one or more channel identifications with the one or moreclient devices 101A-101N through a shard referential table stored in themain database 111. Continuing from the previous example, upon receivingan electronic approval from client device 101B, the group-basedcommunication platform 105 may further update the shard referentialtable stored in the main database 111 based on the organization Xidentification, organization Y identification, and the sharedcommunication channel identification of the newly created databaseshard, such as database shard 113N.

By generating a shared communication channel shard and updating theshard referential table, the present invention provides many technicaladvantages over existing systems, such as solving the union ofidentities issue. Continuing from the “Tony-X/Tony-Z” example above, anexternally shared communication channel between organization X andorganization Z, created based on the present invention, is able toreconcile Tony's two identities, Tony-X and Tony-Z, in two separatedorganization. While updating the shard referential table, systemsstructured in accordance with embodiments of present invention are ableto identify duplicate user identities by, for example, searching andcomparing data associated with each organization. Upon determining thatTony-X and Tony-Y are associated with the same individual, systemsstructured in accordance with embodiments of present invention assign aunified identity to Tony in the shared communication channel shard.Existing systems, on the other hand, are unable to solve the union ofidentities issue, as they fail to create a shared communication channelshard and/or update a shard referential table.

The group-based communication platform 105 may further generate one ormore interfaces for the one or more generated database shards, and maytransmit the one or more interfaces to the client devices 101A-101N.Continuing from the previous example, the group-based communicationplatform 105 may generate a user interface for the database shard 113N,and transmit the user interface to client devices 101A and 101B. In someembodiments, the group-based communication platform 105 may send onlythe appropriate data/interface to client devices 101A and 101B, or mayretrieve and cache the data before sending it to client devices 101A and101, or may compile an interface program that can be used as part ofapps on client devices 101A and 101.

In some preferred and non-limiting embodiments, the referential tablestored in the main database 111 may indicate referential connectionsbetween a group identification and a database shard of database shards113A-113N. Continuing form the previous example, client devices 101A and101C may be both associated with organization X identification, and theshard referential table may indicate that data related to communicationsbetween client devices 101A-101B are stored in database shard 113A.

In some preferred and non-limiting embodiments, when the group-basedcommunication platform 105 receives one or more electronic approvalsfrom one or more client devices 101A-101N, the group-based communicationplatform 105 may update the shard referential table stored in the maindatabase 111 by generating a new referential connection. For example,after receiving an electronic approval to create a shared communicationchannel between organization X and organization Y, the group-basedcommunication platform 105 may update the shard referential table,indicating the referential connection between organization Xidentification, organization Y identification, and the identification ofthe newly generated database shard.

In some preferred and non-limiting embodiments, the group-basedcommunication platform 105 may amplify electronic messages received fromone or more client devices 101A-101N in an externally sharedcommunication channel to other client devices in the same channel usingthe message server 107. For example, the message server 107 may receivean electronic message from client device 101A in association with anexternally shared communication channel. The message server 107 mayquery the network application server 109, which in turn identifies oneor more client devices associated with the externally sharedcommunication channel based on the shard referential table stored in themain database 111. The message server 107 may further transmit theelectronic message to each identified client device.

The above-referenced electronic information exchange provides varioustechnical advantages over existing systems. For example, it allowsinformation retrieval and dispatch of data without the over-burdening ofmessages dispatched to the communication network 103. In addition, therobustness of data, along with the dispatch speed based on theconfiguration of the communication network 103, provides the group-basedcommunication platform 105 the option to utilize either the messageserver 107 or the network application server 109. Further, it providesan option for external applications (developed for the group-basedcommunication platform 105) to use websocket or RPC APIs (which mayfurther use the message server 107 or the network application server109) to emit messages, as further discussed below.

Example Apparatus for Implementing Embodiments of the Present Invention

The message server 107 may be embodied by one or more computing systems,such as apparatus 200 shown in FIG. 2. The apparatus 200 may includeprocessor 202, memory 204, input/output circuitry 206, communicationscircuitry 208, and message amplifier circuitry 210. The apparatus 200may be configured to execute the operations described above with respectto FIG. 1 and below with respect to FIGS. 4-7. Although these components202-210 are described with respect to functional limitations, it shouldbe understood that the particular implementations necessarily includethe use of particular hardware. It should also be understood thatcertain of these components 202-210 may include similar or commonhardware. For example, two sets of circuitries may both leverage use ofthe same processor, network interface, storage medium, or the like toperform their associated functions, such that duplicate hardware is notrequired for each set of circuitries.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 204 via a bus forpassing information among components of the apparatus. The memory 204 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 204 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 204 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus to carry out various functions in accordance with exampleembodiments of the present invention.

The processor 202 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. In some preferred and non-limiting embodiments,the processor 202 may include one or more processors configured intandem via a bus to enable independent execution of instructions,pipelining, and/or multithreading. The use of the term “processingcircuitry” may be understood to include a single core processor, amulti-core processor, multiple processors internal to the apparatus,and/or remote or “cloud” processors.

In some preferred and non-limiting embodiments, the processor 202 may beconfigured to execute instructions stored in the memory 204 or otherwiseaccessible to the processor 202. In some preferred and non-limitingembodiments, the processor 202 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 202 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 202 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 202 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

In some embodiments, the apparatus 200 may include input/outputcircuitry 206 that may, in turn, be in communication with processor 202to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 206 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a client device, a kiosk, or the like.In some embodiments, the input/output circuitry 206 may also include akeyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms. The processorand/or user interface circuitry comprising the processor may beconfigured to control one or more functions of one or more userinterface elements through computer program instructions (e.g., softwareand/or firmware) stored on a memory accessible to the processor (e.g.,memory 204, and/or the like).

The communications circuitry 208 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 200. In this regard, the communications circuitry 208may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 208 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 208 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

Message amplifier circuitry 210 includes hardware configured to copy andamplify electronic messages and associated metadata received from one ormore client devices to other client devices based on the databaseshard(s). The message amplifier circuitry 210 may utilize processingcircuitry, such as the processor 202, to perform these actions. However,it should also be appreciated that, in some embodiments, the messageamplifier circuitry 210 may include a separate processor, speciallyconfigured Field Programmable Gate Array (FPGA), or Application SpecificIntegrated Circuit (ASIC) for performing the functions described herein.The message amplifier circuitry 210 may be implemented using hardwarecomponents of the apparatus configured by either hardware or softwarefor implementing these planned functions.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 200. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

The network application server 109 may be embodied by one or morecomputing systems, such as apparatus 300 shown in FIG. 3. The apparatus300 may include processor 301, memory 303, input/output circuitry 305,communications circuitry 307, database circuitry 309, interfacegeneration circuitry 311, and referential table generation circuitry313. The apparatus 300 may be configured to execute the operationsdescribed above with respect to FIG. 1 and below with respect to FIGS.4-7. Although these components 301-313 are described with respect tofunctional limitations, it should be understood that the particularimplementations necessarily include the use of particular hardware. Itshould also be understood that certain of these components 301-313 mayinclude similar or common hardware. For example, two sets of circuitriesmay both leverage use of the same processor, network interface, storagemedium, or the like to perform their associated functions, such thatduplicate hardware is not required for each set of circuitries.

In some embodiments, the processor 301 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 303 via a bus forpassing information among components of the apparatus. The memory 303 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 303 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 303 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus 300 to carry out various functions in accordance with exampleembodiments of the present invention.

The processor 301 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. In some preferred and non-limiting embodiments,the processor 301 may include one or more processors configured intandem via a bus to enable independent execution of instructions,pipelining, and/or multithreading.

In some preferred and non-limiting embodiments, the processor 301 may beconfigured to execute instructions stored in the memory 303 or otherwiseaccessible to the processor 301. In some preferred and non-limitingembodiments, the processor 301 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 301 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 301 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 301 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

In some embodiments, the apparatus 300 may include input/outputcircuitry 305 that may, in turn, be in communication with processor 301to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 305 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a client device, a kiosk, or the like.In some embodiments, the input/output circuitry 305 may also include akeyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms.

The communications circuitry 307 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 300. In this regard, the communications circuitry 307may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 307 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 307 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

Database circuitry 309 includes hardware configured to manage one ormore network databases, including database shards 113A-113N and the maindatabase 111. The database circuitry 309 may utilize processingcircuitry, such as the processor 301, to perform these actions. Thedatabase circuitry 309 may transmit data to the interface generationcircuitry 311 and referential table generation circuitry 313. In somepreferred and non-limiting embodiments, the data sent may be associatedwith the one or more database shards 113A-113N.

In some embodiments, the database circuitry 309 may include a separateprocessor, specially configured Field Programmable Gate Array (FPGA), orApplication Specific Integrated Circuit (ASIC). In some implementations,the referential table generation circuitry 313 and the interfacegeneration circuitry 311, described below, may be sub-circuitriesbelonging to database circuitry 309. The database circuitry 309 may beimplemented using hardware components of the apparatus configured byeither hardware or software for implementing the functions describedherein.

The referential table generation circuitry 313 includes hardwareconfigured to generate and update shard referential table store in themain database 111. The referential table generation circuitry 313 mayutilize processing circuitry, such as the processor 301, to performthese actions. However, it should also be appreciated that, in someembodiments, the referential table generation circuitry 313 may includea separate processor, specially configured Field Programmable Gate Array(FPGA), or Application Specific Integrated Circuit (ASIC) for performingthe functions described herein. The referential table generationcircuitry 313 may be implemented using hardware components of theapparatus configured by either hardware or software for implementingthese planned functions.

The interface generation circuitry 311 includes hardware configured togenerate communication channel interfaces for client devices 101A-101N.The interface generation circuitry 311 may utilize processing circuitry,such as the processor 301, to perform these actions. However, it shouldalso be appreciated that, in some embodiments, the interface generationcircuitry 311 may include a separate processor, specially configuredField Programmable Gate Array (FPGA), or Application Specific IntegratedCircuit (ASIC) for performing the functions described herein. Theinterface generation circuitry 311 may be implemented using hardwarecomponents of the apparatus configured by either hardware or softwarefor implementing these planned functions.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 300. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

The term “circuitry” should be understood broadly to include hardwareand, in some embodiments, software for configuring the hardware. Withrespect to components of the apparatus, the term “circuitry” as usedherein should therefore be understood to include particular hardwareconfigured to perform the functions associated with the particularcircuitry as described herein. For example, in some embodiments,“circuitry” may include processing circuitry, storage media, networkinterfaces, input/output devices, and the like. In some embodiments,other elements of the apparatus 200 may provide or supplement thefunctionality of particular circuitry. For example, the processor 202may provide processing functionality, the memory 204 may provide storagefunctionality, the communications circuitry 208 may provide networkinterface functionality, and the like. Similarly, other elements of theapparatus 300 may provide or supplement the functionality of particularcircuitry. For example, the processor 301 may provide processingfunctionality, the memory 303 may provide storage functionality, thecommunications circuitry 307 may provide network interfacefunctionality, and the like.

As will be appreciated, any such computer program instructions and/orother type of code may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor or other programmable circuitry that execute thecode on the machine creates the means for implementing variousfunctions, including those described herein.

As described above and as will be appreciated based on this disclosure,embodiments of the present invention may be configured as methods,mobile devices, backend network devices, and the like. Accordingly,embodiments may comprise various means including entirely of hardware orany combination of software and hardware. Furthermore, embodiments maytake the form of a computer program product on at least onenon-transitory computer-readable storage medium having computer-readableprogram instructions (e.g., computer software) embodied in the storagemedium. Any suitable computer-readable storage medium may be utilizedincluding non-transitory hard disks, CD-ROMs, flash memory, opticalstorage devices, or magnetic storage devices.

Example Data Flows for Generating Externally Shared CommunicationChannels

FIGS. 4, 5, 6, and 7 illustrate various interactions between one or moreclient devices 101A-101N and the group-based communication platform 105in generating an externally shared communication channel based onwhether the initiator and the target of the shared communication channelgeneration query is an administrator of a group.

The term “administrator” refers to a subscriber of a communicationchannel who has authority to manage the communication channel and makedecisions on behalf of other subscribers regarding various maintenancetasks. For example, a group administrator may have the authority to seta communication channel as either “public” or “private.” As anotherexample, when receiving a request to create an externally sharedcommunication channel, only a group administrator has the authority toaccept the request on behalf of the group. In some embodiments, thesystem uses a flag on data associated with a user to indicate whetherthe user is a member of a group.

Referring now to FIG. 4, the process 400 illustrates an example processof generating an externally shared communication channel when anon-administrator of group A submits a request to create a sharedcommunication channel targeting a non-administrator of group B.

The process 400 starts at step 402, where a non-administrator of group Asubmits a request to create an externally shared communication channel.The system automatically creates an invite for the non-administrator ofgroup A, and shares the invite with the non-administrator of group B atstep 404. Here, an invite is an electronic indication of the request tocreate an externally shared communication channel. For example, aninvite can take the form of a Uniform Resource Locator (URL) that linksto a webpage containing details of the request. In some embodiments, theURL link may expire after a predetermined amount of time has passedsince the URL link has been transmitted. For example, a user may set theURL to expire after 24 hours of transmission.

The non-administrator of group B receives the invite at step 406. Atstep 408, the non-administrator of group B makes an initial decision asto whether to add a channel. If the non-administrator of group B decidesnot to add the channel, then the non-administrator of group A receivesan electronic indication that the request has been denied at step 410.

If the non-administrator of group B decides to add the channel, then thesystem automatically forwards the request to create an externally sharedcommunication channel to an administrator of group A and anadministrator of group B at steps 412 and 414, respectively. If theadministrator of group A does not approve the request at step 416, thenthe non-administrators of group A and group B receive electronicindications that the request has been denied at step 420. Similarly, ifthe administrator of group B does not approve the request at step 418,then the non-administrators of group A and group B receive electronicindications that the request has been denied at step 420.

When both the administrator of group A and the administrator of group Bapprove the request, the system proceeds with the creation of anexternally shared communication channel at step 422.

Referring now to FIG. 5, the process 500 illustrates an example processof generating an externally shared communication channel when anon-administrator of group A submits a request to create a sharedcommunication channel targeting an administrator of group B.

The process 500 starts at step 501, where a non-administrator of group Asubmits a request to create an externally shared communication channel.The system automatically creates an invite for the non-administrator ofgroup A, and shares the invite with the administrator of group B at step503.

Upon sharing the invite with the administrator of group B, the systemautomatically generates a request for approval at step 505. Theadministrator of group B then decides whether to approve the request tocreate an externally shared communication channel at step 507. If theadministrator of group B does not approve the request, then thenon-administrator of group A receives an electronic indication that therequest has been denied at step 509.

If the administrator of group B approves the request, then the systemautomatically forwards the request to an administrator of group A atstep 511. If the administrator of group A does not approve the requestat step 513, then both the administrator and the non-administrator ofgroup B receive electronic indications that the request has been deniedat step 515.

If the administrator of group A approves the request at step 513, thesystem proceeds with the creation of an externally shared communicationchannel at step 517.

Referring now to FIG. 6, the process 600 illustrates an example processof generating an externally shared communication channel when anadministrator of group A submits a request to create a sharedcommunication channel targeting a non-administrator of group B.

The process 600 starts at step 602, where an administrator of group Asubmits a request to create an externally shared communication channel.The system automatically creates an invite for the administrator ofgroup A, and shares the invite with the non-administrator of group B atstep 604.

The non-administrator of group B receives the invite at step 606. Atstep 608, the non-administrator of group B makes an initial decision asto whether to add a channel. If the non-administrator of group B decidesnot to add the channel, then the administrator of group A receives anelectronic indication that the request has been denied at step 610.

If the non-administrator of group B decides to add the channel, then thesystem automatically forwards the request to create externally sharedcommunication channel to the administrator of group A and anadministrator of group B at steps 612 and 614, respectively. If theadministrator of group A does not approve the request at step 616, thenthe non-administrators of group B receives an electronic indication thatthe request has been denied at step 620. Similarly, if the administratorof group B does not approve the request at step 618, then thenon-administrator of group B receives an electronic indication that therequest has been denied at step 620.

When both the administrator of group A and the administrator of group Bapprove the request, the system proceeds with the creation of anexternally shared communication channel at step 622.

Referring now to FIG. 7, the process 700 illustrates an example processof generating an externally shared communication channel when anadministrator of group A submits a request to create a sharedcommunication channel targeting an administrator of group B.

The process 700 starts at step 701, where an administrator of group Asubmits a request to create an externally shared communication channel.The system automatically creates an invite for the administrator ofgroup A, and shares the invite with an administrator of group B at step703.

Upon sharing the invite with the administrator of group B, the systemautomatically generates a request for approval at step 705. Theadministrator of group B then decides whether to approve the request tocreate an externally shared communication channel at step 707. If theadministrator of group B does not approve the request, then theadministrator of group A receives an electronic indication that therequest has been denied at step 709.

If the administrator of group B approves the request, then the systemautomatically forwards the request to the administrator of group A atstep 711. If the administrator of group A does not approve the requestat step 713, then the administrator of group B receives an electronicindication that the request has been denied at step 715. If theadministrator of group A approves the request, the system proceeds withthe creation of an externally shared communication channel at step 717.

Example Implementation for Externally Shared Communication Channels

FIGS. 8A, 8B, 8C, and 8D illustrate various elements of examplecommunication channel interfaces according to some embodiments of thepresent invention.

Referring now to FIG. 8A, an example communication channel interface800A is shown. The communication channel interface 800A includes a username box 802, indicating the current user account associated with thecommunication channel interface 800A.

The communication channel interface 800A also may also include a channellist pane, which may include an externally shared communication channellist subpane 804. The externally shared communication channel listsubpane 804 allows a user to quickly and easily navigate all externallyshared communication channels that the user has subscribed to. Forexample, as shown in FIG. 8A, the user Tony has subscribed to externallyshared communication channels C1, C2, C3, and C4, which are indicated byan overlapping square symbol to the right of each channel name. Eachgroup may set its preference as to the name of an externally sharedcommunication channel in the externally shared communication channellist subpane 804.

The channel list pane of the communication channel interface 800A mayfurther include an internally shared communication channel list subpane806, which lists all internally shared communication channels that auser has subscribed to. In contrast to those listed in the externallyshared communication channel list subpane 804, all channels in theinternally shared communication channel list subpane 806 are shared withother users within the same group or organization.

A channel in the externally shared communication channel list subpane804 or the internally shared communication channel list subpane 806 canbe a private channel or a public channel. The status of the channel maybe indicated by an icon to the left of the channel name. For example, asshown in the internally shared communication channel list subpane 806 ofFIG. 8A, channels C5 and C6 each has a pound sign next to its name,which indicates that they are public channels; channels C7 and C8 eachhas a lock sign next to its name, which indicates that they are privatechannels.

The communication channel interface 800A further includes a channeltitle box 810 and a direct message pane 808. The direct message pane 808lists all the members who share the same channel as the user. Forexample, as shown in the direct message pane 808 of FIG. 8A, the usermay send a direct message to Beth or Carl, who share the same channel C1as the user. In connection with the direct message pane 808, thecommunication channel interface 800A may further include a flexpane 816,which may display information such as member directory of a group. Themember directory may be browseable, searchable, and filterable throughthe flexpane 816.

In some embodiments, the display of the member directory may bedetermined based on the retention settings. The retention setting mayfurther determine which applications are installed on the channel, whichfeatures are enabled for the channel, and other preferences regardingwhich users are allowed to control the channel.

In addition, the communication channel interface 800A includes a channelmessaging pane 812, which displays text, images, and other history dataassociated with the communication channel. In some embodiments, thehistory data may include changes to membership, such as when a user joinor leave a channel, when an application is installed or removed from achannel.

In some embodiments, the viewing privilege settings of some content(i.e. who may view these content) in the channel messaging pane 812 maybe specific to the user and hidden from public view. For example, when auser use a command to interact privately with an application or a bot,such activities may be hidden from the public view. A user may alsochoose to make such activities viewable by the public.

In some embodiments, the viewing privilege settings may be specific tothe team and/or applications installed on the team. For example, whenTony from organization X wants to use a command, the command menu willonly show commands from applications that have been installed onorganization X.

A user may use the channel input box 814 to contribute to thecommunication channel, which would be displayed in the channel messagingpane 812. The channel input box 814 may provide autocomplete function,which automatically recognizes user name, channel name, and otherinformation as a user types in the channel input box 814. In someembodiments, the auto-complete bot may also recognize the names ofapplications and other bots to further interact with the channel. Thechannel input box 814 may also provide message input warnings when auser is in an externally shared communication channel, alerting the userthat any information he or she contributed may be seen by members ofanother group or organization. Referring now to FIG. 8B, an example usericon 800B is shown. The user icon 800B may include a user avatar 801 anda group icon 803. The user avatar 801 may indicate the identity of auser, and the group icon 803 may indicate the group that the user isassociated with. In some preferred and non-limiting embodiments, theuser avatar 801 may have a size of 72 px by 72 px, with 4 px roundedcorners. The group icon 803 may have a size of 22 px by 22 px, with 4 pxrounded corners, 1 px inner border, and 3 px outer border.

Referring now to FIG. 8C, an example communication channel interface800C is shown. The communication channel interface 800C may include agroup member profile card 818, which may further include a profilepicture 820 of a group member, a group identification box 822 andfunction buttons 824. The group identification box 822 may includeinformation such as the name of the group that the group member isassociated with. The function buttons 824 may allow the user to performvarious functions, such as sending a direct message to the group member.

Referring now to FIG. 8D, the user interface 800D illustrates an exampleinterface for direct messaging with a group member. The user interface800D may include a member name box 810′, which indicates the name of thegroup member with whom the user is direct messaging. The communicationpane 812′ shows direct messaging history between the user and the groupmember. The user interface 800D may further includes a direct messageprofile pane 826, which may include a user information section 828 and arelated information section 830. The direct message profile pane 826enables a user to quickly and easily recognize basic information aboutthe group member with whom the user is direct messaging.

Example Application Programming Interface (API) Design for ImplementingEmbodiments of the Present Invention

In some embodiments, systems structured in accordance with embodimentsof the present invention may provide Application Programming Interfaces(APIs) that enable configurability of applications and bots in anexternally shared communication channel.

Existing systems are plagued by technical limitations. For example, someexisting systems fail to roll up member teams in an externally sharedcommunication channel, while others fail to emit events to users whosegroup-based communication channels are not stored on the same shard.

Various embodiments of the present invention provide technicalimprovements over existing systems. As described above, a sharedcommunication channel shard may be generated to store data related to anexternally shared communication channel. In some embodiments of thepresent invention, an events subscription table (e.g.,“event_subscriptions_types”) may be stored in the shared communicationchannel shard. The events subscription table stores informationregarding whether to emit events to members in an externally sharedcommunication channel. To solve the above-identified technicaldifficulties, the events subscription table may be updated to include a“resource_id” column and a “resource_type” column. The “resource_id”column stores the identification of the resource (e.g. event), and the“resource_type” column identifies the type of the resource (e.g.,whether the event is subscribed by teams whose group-based communicationchannels are stored on different shards). By utilizing these twocolumns, embodiments of the present invention solve the issues of whereand how to store consolidated event registration information forapplications installed on a group-based communication channel.Continuing from the “Tony to Frank” example, the externally sharedcommunication channel may utilize the “resource_type” column and the“resource_id” column to store information regarding whether organizationX and/or organization Y is subscribed to a particular resource (i.e.event).

The programming code below provides alteration of the“event_subscriptions_types” table to include “resrouce_type” and“resrouce_id” columns:

-   -   ALTER TABLE event_subscriptions_types ADD COLUMN resource_type        varchar(25) NOT NULL AFTER team_id    -   ALTER TABLE event_subscriptions_types ADD COLUMN resource_id        bigint(20) UNSIGNED NOT NULL AFTER resource_type    -   ALTER TABLE event_subscriptions_types ADD COLUMN ext_team_id        bigint(20) UNSIGNED NOT NULL AFTER team_id    -   ALTER TABLE event_subscriptions_types DROP PRIMARY KEY, ADD        PRIMARY KEY event_subscription_id, team_id, event_type,        resource_type, resource_id)

In some embodiments of the present invention, a “channel_id” column andan “event_subscription_id” column may be added to the“event_subscriptions_types” table. The “channel_id” column identifiesthe group-based communication channel, and the “event_subscription_id”identifies the events that each group-based communication channel issubscribed to. Continuing from the “Tony to Frank” example, the“channel_id” column and the “event_subscription_id” column storeinformation regarding what events each of organization X andorganization Y has subscribed to.

Further, some embodiments of the present invention may also create a newtable in the shared communication channel shard, such as“event_subscriptions_ext_shared,” to separately store event subscriptioninformation for each team. The programming code below provides thecreation of the “event_subscriptions_ext_shared” table.

-   -   CREATE TABLE ‘event_subscriptions_ext_shared’ (    -   ‘subscription_team_id’ bigint(20) UNSIGNED NOT NULL,    -   ‘channel_id’ bigint(20) UNSIGNED NOT NULL,    -   ‘api_app_id’ bigint(20) UNSIGNED NOT NULL,    -   ‘event_type’ varchar(255) NOT NULL    -   PRIMARY KEY (‘subscription_t_team_id’, ‘channel_id’,        ‘event_type’)    -   )ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

Additional Implementation Details

Although example processing systems have been described in FIGS. 2 and3, implementations of the subject matter and the functional operationsdescribed herein can be implemented in other types of digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them.

Embodiments of the subject matter and the operations described hereincan be implemented in digital electronic circuitry, or in computersoftware, firmware, or hardware, including the structures disclosed inthis specification and their structural equivalents, or in combinationsof one or more of them. Embodiments of the subject matter describedherein can be implemented as one or more computer programs, i.e., one ormore modules of computer program instructions, encoded oncomputer-readable storage medium for execution by, or to control theoperation of, information/data processing apparatus. Alternatively, orin addition, the program instructions can be encoded on anartificially-generated propagated signal, e.g., a machine-generatedelectrical, optical, or electromagnetic signal, which is generated toencode information/data for transmission to suitable receiver apparatusfor execution by an information/data processing apparatus. Acomputer-readable storage medium can be, or be included in, acomputer-readable storage device, a computer-readable storage substrate,a random or serial access memory array or device, or a combination ofone or more of them. Moreover, while a computer-readable storage mediumis not a propagated signal, a computer-readable storage medium can be asource or destination of computer program instructions encoded in anartificially-generated propagated signal. The computer-readable storagemedium can also be, or be included in, one or more separate physicalcomponents or media (e.g., multiple CDs, disks, or other storagedevices).

The operations described herein can be implemented as operationsperformed by an information/data processing apparatus oninformation/data stored on one or more computer-readable storage devicesor received from other sources.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includespecial purpose logic circuitry, e.g., an FPGA (field programmable gatearray) or an ASIC (Application Specific Integrated Circuit). Theapparatus can also include, in addition to hardware, code that createsan execution environment for the computer program in question, e.g.,code that constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, a cross-platform runtimeenvironment, a virtual machine, or a combination of one or more of them.The apparatus and execution environment can realize various differentcomputing model infrastructures, such as web services, distributedcomputing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor information/data (e.g., one or more scripts stored in a markuplanguage document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub-programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described herein can be performed by oneor more programmable processors executing one or more computer programsto perform actions by operating on input information/data and generatingoutput. Processors suitable for the execution of a computer programinclude, by way of example, both general and special purposemicroprocessors, and any one or more processors of any kind of digitalcomputer. Generally, a processor will receive instructions andinformation/data from a read-only memory, a random access memory, orboth. The essential elements of a computer are a processor forperforming actions in accordance with instructions and one or morememory devices for storing instructions and data. Generally, a computerwill also include, or be operatively coupled to receive information/datafrom or transfer information/data to, or both, one or more mass storagedevices for storing data, e.g., magnetic, magneto-optical disks, oroptical disks. However, a computer need not have such devices. Devicessuitable for storing computer program instructions and information/datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described herein can be implemented on a computer having adisplay device, e.g., a CRT (cathode ray tube) or LCD (liquid crystaldisplay) monitor, for displaying information/data to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described herein can be implemented ina computing system that includes a back-end component, e.g., as aninformation/data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aclient device having a graphical user interface or a web browser throughwhich a user can interact with an implementation of the subject matterdescribed herein, or any combination of one or more such back-end,middleware, or front-end components. The components of the system can beinterconnected by any form or medium of digital information/datacommunication, e.g., a communication network. Examples of communicationnetworks include a local area network (“LAN”) and a wide area network(“WAN”), an inter-network (e.g., the Internet), and peer-to-peernetworks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits information/data (e.g., an HTML page) toa client device (e.g., for purposes of displaying information/data toand receiving user input from a user interacting with the clientdevice). Information/data generated at the client device (e.g., a resultof the user interaction) can be received from the client device at theserver.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as description offeatures specific to particular embodiments of particular inventions.Certain features that are described herein in the context of separateembodiments can also be implemented in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiment can also be implemented in multipleembodiments separately or in any suitable sub-combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults, unless described otherwise. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system components in the embodiments describedabove should not be understood as requiring such separation in allembodiments, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults, unless described otherwise. In certain implementations,multitasking and parallel processing may be advantageous.

CONCLUSION

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing description and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation, unlessdescribed otherwise.

That which is claimed:
 1. A computer-implemented method for creating ashared communication channel in a group-based communication platform,the computer-implemented method comprising: receiving, from a firstclient associated with a first organization identifier, a sharedcommunication channel generation request associated with the firstorganization identifier and a second organization identifier, whereinthe shared communication channel generation request is associated with ashared communication channel identifier; transmitting, to a secondclient associated with the second organization identifier, a sharedcommunication channel acceptance request, wherein the sharedcommunication channel acceptance request is associated with the sharedcommunication channel identifier; receiving a shared communicationchannel acceptance notification, wherein the shared communicationchannel acceptance notification includes an electronic approval toassociate the shared communication channel identifier with the firstorganization identifier and the second organization identifier; andtransmitting, to each of the first client and the second client andbased at least in part on receiving the shared communication channelacceptance notification, a shared group-based communication channelinterface of the shared communication channel.
 2. Thecomputer-implemented method of claim 1, further comprising: determiningthat the first client and the second client are each associated with anon-administrator status indicator; transmitting, to a third clientassociated with the first organization identifier and a firstadministrator status indicator, a first shared communication channelapproval request; transmitting, to a fourth client associated with thesecond organization identifier and a second administrator statusindicator, a second shared communication channel approval request;receiving a first shared communication channel approval notificationfrom the third client; and receiving a second shared communicationchannel approval notification from the fourth client, whereintransmitting the shared group-based communication channel interface toeach of the first client and the second client is further based at leastin part on receiving the first shared communication channel approvalnotification and the second shared communication channel approvalnotification.
 3. The computer-implemented method of claim 1, furthercomprising: determining that the first client is associated with anon-administrator status indicator and the second client is associatedwith a first administrator status indicator; transmitting, to a thirdclient associated with the first organization identifier and a secondadministrator status indicator, a shared communication channel approvalrequest; and receiving a shared communication channel approvalnotification from the third client, wherein transmitting the sharedgroup-based communication channel interface to each of the first clientand the second client is further based at least in part on receiving theshared communication channel approval notification.
 4. Thecomputer-implemented method of claim 1, further comprising: determiningthat the first client is associated with a first administrator statusindicator and the second client is associated with a non-administratorstatus indicator; transmitting, to a third client associated with thesecond organization identifier and a second administrator statusindicator, a shared communication channel approval request; andreceiving a shared communication channel approval notification from thethird client, wherein transmitting the shared group-based communicationchannel interface to each of the first client and the second client isfurther based at least in part on receiving the shared communicationchannel approval notification.
 5. The computer-implemented method ofclaim 1, wherein the first client and the second client are eachassociated with an administrator status indicator.
 6. Thecomputer-implemented method of claim 1, wherein the first organizationidentifier is associated with a first organization and the secondorganization identifier is associated with a second organization that isdifferent than the first organization, and wherein the sharedcommunication channel is externally shared.
 7. The computer-implementedmethod of claim 1, wherein the first client and the second client areeach permitted to at least one of post or view one or more messagesposted to the shared communication channel.
 8. A system comprising: oneor more processors; and one or more non-transitory computer-readablemedia storing instructions that, when executed by the one or moreprocessors, cause the system to perform operations comprising:receiving, from a first client associated with a first organizationidentifier, a shared communication channel generation request associatedwith the first organization identifier and a second organizationidentifier, wherein the shared communication channel generation requestis associated with a shared communication channel identifier;transmitting, to a second client associated with the second organizationidentifier, a shared communication channel acceptance request, whereinthe shared communication channel acceptance request is associated withthe shared communication channel identifier; receiving a sharedcommunication channel acceptance notification, wherein the sharedcommunication channel acceptance notification includes an electronicapproval to associate the shared communication channel identifier withthe first organization identifier and the second organizationidentifier; and transmitting, to each of the first client and the secondclient and based at least in part on receiving the shared communicationchannel acceptance notification, a shared group-based communicationchannel interface of the shared communication channel.
 9. The system ofclaim 8, the operations further comprising: determining that the firstclient and the second client are each associated with anon-administrator status indicator; transmitting, to a third clientassociated with the first organization identifier and a firstadministrator status indicator, a first shared communication channelapproval request; transmitting, to a fourth client associated with thesecond organization identifier and a second administrator statusindicator, a second shared communication channel approval request;receiving a first shared communication channel approval notificationfrom the third client; and receiving a second shared communicationchannel approval notification from the fourth client, whereintransmitting the shared group-based communication channel interface toeach of the first client and the second client is further based at leastin part on receiving the first shared communication channel approvalnotification and the second shared communication channel approvalnotification.
 10. The system of claim 8, the operations furthercomprising: determining that the first client is associated with anon-administrator status indicator and the second client is associatedwith a first administrator status indicator; transmitting, to a thirdclient associated with the first organization identifier and a secondadministrator status indicator, a shared communication channel approvalrequest; and receiving a shared communication channel approvalnotification from the third client, wherein transmitting the sharedgroup-based communication channel interface to each of the first clientand the second client is further based at least in part on receiving theshared communication channel approval notification.
 11. The system ofclaim 8, the operations further comprising: determining that the firstclient is associated with a first administrator status indicator and thesecond client is associated with a non-administrator status indicator;transmitting, to a third client associated with the second organizationidentifier and a second administrator status indicator, a sharedcommunication channel approval request; and receiving a sharedcommunication channel approval notification from the third client,wherein transmitting the shared group-based communication channelinterface to each of the first client and the second client is furtherbased at least in part on receiving the shared communication channelapproval notification.
 12. The system of claim 8, wherein the firstclient and the second client are each associated with an administratorstatus indicator.
 13. The system of claim 8, wherein the firstorganization identifier is associated with a first organization and thesecond organization identifier is associated with a second organizationthat is different than the first organization, and wherein the sharedcommunication channel is externally shared.
 14. The system of claim 8,wherein the first client and the second client are each permitted to atleast one of post or view one or more messages posted to the sharedcommunication channel.
 15. One or more non-transitory computer-readablemedia storing instructions that, when executed by one or moreprocessors, cause the one or more processors to perform operationscomprising: receiving, from a first client associated with a firstorganization identifier, a shared communication channel generationrequest associated with the first organization identifier and a secondorganization identifier, wherein the shared communication channelgeneration request is associated with a shared communication channelidentifier; transmitting, to a second client associated with the secondorganization identifier, a shared communication channel acceptancerequest, wherein the shared communication channel acceptance request isassociated with the shared communication channel identifier; receiving ashared communication channel acceptance notification, wherein the sharedcommunication channel acceptance notification includes an electronicapproval to associate the shared communication channel identifier withthe first organization identifier and the second organizationidentifier; and transmitting, to each of the first client and the secondclient and based at least in part on receiving the shared communicationchannel acceptance notification, a shared group-based communicationchannel interface of the shared communication channel.
 16. The one ormore non-transitory computer-readable media of claim 15, the operationsfurther comprising: determining that the first client and the secondclient are each associated with a non-administrator status indicator;transmitting, to a third client associated with the first organizationidentifier and a first administrator status indicator, a first sharedcommunication channel approval request; transmitting, to a fourth clientassociated with the second organization identifier and a secondadministrator status indicator, a second shared communication channelapproval request; receiving a first shared communication channelapproval notification from the third client; and receiving a secondshared communication channel approval notification from the fourthclient, wherein transmitting the shared group-based communicationchannel interface to each of the first client and the second client isfurther based at least in part on receiving the first sharedcommunication channel approval notification and the second sharedcommunication channel approval notification.
 17. The one or morenon-transitory computer-readable media of claim 15, the operationsfurther comprising: determining that the first client is associated witha non-administrator status indicator and the second client is associatedwith a first administrator status indicator; transmitting, to a thirdclient associated with the first organization identifier and a secondadministrator status indicator, a shared communication channel approvalrequest; and receiving a shared communication channel approvalnotification from the third client, wherein transmitting the sharedgroup-based communication channel interface to each of the first clientand the second client is further based at least in part on receiving theshared communication channel approval notification.
 18. The one or morenon-transitory computer-readable media of claim 15, the operationsfurther comprising: determining that the first client is associated witha first administrator status indicator and the second client isassociated with a non-administrator status indicator; transmitting, to athird client associated with the second organization identifier and asecond administrator status indicator, a shared communication channelapproval request; and receiving a shared communication channel approvalnotification from the third client, wherein transmitting the sharedgroup-based communication channel interface to each of the first clientand the second client is further based at least in part on receiving theshared communication channel approval notification.
 19. The one or morenon-transitory computer-readable media of claim 15, wherein the firstclient and the second client are each associated with an administratorstatus indicator.
 20. The one or more non-transitory computer-readablemedia of claim 15, wherein the first client and the second client areeach permitted to at least one of post or view one or more messagesposted to the shared communication channel.